The Connections to MBG page initiates connections to MBGs. Typically, a connection to the local MBG is created automatically.
NOTE: You must verify the connection to the MBG to guarantee security.
You can only connect an MBG if its Web Service has been activated in the MBG server manager. While MiCollab is running in the browser, you can open the MBG Web Services in a second browser tab.
To add and verify a new MBG connection:
Click Create new connection and enter the following information:
Setting |
Description |
Name |
Descriptive name for the MBG. |
Host |
Hostname or IP address. |
Click Save and send AuthRequest. The connection is populated with a Token key and a popup window appears.
Click OK in the popup window to allow the connection to the MBG.
Click Authorize. The MiCollab Login page is displayed.
Enter the MiCollab server manager Username and Password and click Login.
After you enter the credentials, the popup-window closes and the connection to the MBG is updated with the credentials.
NOTE: Creating or re-authenticating an MBG connection is limited to primary administrator account.
If you accidentally close the popup-window or if it does not open (for example, due to a browser issue) click Authenticate on the Connection page to open the pop-up window. This button is only present if the connection to the MBG has not been verified.
Click Connections
to MBGs. The table on the Connections
to MBGs page will have been updated with the following information:
Setting |
Description |
ID |
This is the local identifier number for an MBG. It also indicates the order in which MBGs were added. |
Name |
Descriptive name for the MBG. |
Hostname |
Hostname or IP address. Required to enable Client DeploYment to request the connection. |
Token ID |
This string is needed to verify the connection between the Client Deployment application and the MBG. |
Verified |
This field indicates if the verification process has been completed for the connection to this MBG. |
Expires in Days |
This field displays the number of days before the Token ID expires at which time the connection must be re-authenticated. |
NOTE: The authentication is valid for one year. MBG connections (local and external) that are going to expire (28 days before expiration) will be automatically renewed.
NOTE: Events are raised before and on the date of expiry. Make sure to regularly check the Event viewer or configure e-mail alerts.
At expiration date: Major (orange)
Two weeks before expiration date: Minor (yellow)
Four weeks before expiration date: Warning (blue)